Conversation
…roject on OCP Signed-off-by: Anatolii Bazko <abazko@redhat.com>
tolusha
requested review from
SDawley,
dkwon17,
ibuziuk and
mkuznyetsov
as code owners
…roject on OCP Signed-off-by: Anatolii Bazko <abazko@redhat.com>
rohanKanojia
approved these changes
Mar 23, 2026
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rohanKanojia, tolusha The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Author
|
Hello @cgruver |
|
New changes are detected. LGTM label has been removed. |
Contributor
Author
|
/retest |
tolusha
added a commit
to eclipse-che/che-docs
that referenced
this pull request
Mar 24, 2026
Document the new `createNamespaceDirectly` CheCluster CR field that allows administrators to create standard Kubernetes Namespaces directly on OpenShift instead of using the ProjectRequest API. Related: eclipse-che/che-operator#2104 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Closed
3 tasks
tolusha
added a commit
to eclipse-che/che-docs
that referenced
this pull request
Mar 25, 2026
Document the new `createNamespaceDirectly` CheCluster CR option that allows creating standard Kubernetes namespaces instead of using the OpenShift ProjectRequest API. Related: eclipse-che/che-operator#2104 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Closed
3 tasks
tolusha
added a commit
to eclipse-che/che-docs
that referenced
this pull request
Mar 25, 2026
Add a procedure article documenting the new `createNamespaceDirectly` CheCluster CR option that allows administrators to configure Che to create standard Kubernetes Namespaces instead of using the OpenShift ProjectRequest API. Source: eclipse-che/che-operator#2104 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
5 tasks
tolusha
added a commit
to eclipse-che/che-docs
that referenced
this pull request
Mar 25, 2026
Add a procedure article for the new `createNamespaceDirectly` CheCluster CR field that allows administrators to bypass the OpenShift ProjectRequest API and create standard Kubernetes Namespaces directly for user workspaces. Related: eclipse-che/che-operator#2104 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…roject on OCP
What does this PR do?
Option to have devspaces operator create namespace instead of project on OCP
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
https://issues.redhat.com/browse/CRW-9951
How to test this PR?
See eclipse-che/che-server#973
Common Test Scenarios
PR Checklist
As the author of this Pull Request I made sure that:
Reviewers
Reviewers, please comment how you tested the PR when approving it.